Skip to main content

This is a new service – your feedback will help us to improve it.

London Borough of Lewisham

Article 4 direction area

There is a problem

  • 78 issue of type invalid category value

Brockley Rise Parade

reference
Bro2
name
Brockley Rise Parade
article-4-direction
permitted-development-rights

undefined

Class e
uprns
address-texts
geometry
MULTIPOLYGON (((-0.042422 51.442398,-0.042400 51.442373,-0.042241 51.442354,-0.042202 51.442485,-0.042222 51.442489,-0.042213 51.442523,-0.042297 51.442534,-0.042289 51.442573,-0.042183 51.442564,-0.042163 51.442650,-0.042362 51.442651,-0.042422 51.442398)),((-0.042866 51.442364,-0.042760 51.442393,-0.042706 51.442429,-0.042641 51.442532,-0.042550 51.442791,-0.042567 51.442943,-0.042588 51.442957,-0.042818 51.442959,-0.042819 51.442919,-0.042745 51.442920,-0.042745 51.442890,-0.042763 51.442888,-0.042761 51.442861,-0.042796 51.442860,-0.042793 51.442796,-0.042867 51.442795,-0.042866 51.442765,-0.042899 51.442764,-0.042898 51.442725,-0.042782 51.442722,-0.042798 51.442681,-0.042840 51.442683,-0.042858 51.442645,-0.042976 51.442659,-0.042960 51.442615,-0.042848 51.442604,-0.042855 51.442580,-0.042743 51.442565,-0.042748 51.442546,-0.042837 51.442561,-0.042842 51.442550,-0.042827 51.442545,-0.042835 51.442528,-0.042944 51.442559,-0.042959 51.442531,-0.042833 51.442456,-0.042917 51.442453,-0.042866 51.442364)))
point
POINT (-0.042617 51.442633)
notes
entry-date
2026-02-25
start-date
end-date

How to fix this issue

Your data is missing a permitted-development-rights.

The Article 4 direction area guidance explains how to fix the issue:

permitted-development-rights

A list of the permitted development rights withdrawn by the article 4 direction.

Separate the rights in the list using semicolons.

Only use rights from our permitted development right dataset. If the area withdraws a permitted development right that is not in our dataset, email digitalland@communities.gov.uk.

Example: 3D;3M;11B

How to improve London Borough of Lewisham’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL